Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Description

Several modules still documented older Python minimums (for example 3.5, 3.8, 3.9, 3.9.19, 3.10), which is inconsistent with the SDK requirement and can cause confusion for users.

Ensures module documentation accurately reflects the minimum Python version needed when using the declared SDK version.

Validation

• Verified there are no remaining module requirement entries below python >= 3.12 in updated targets.
• Confirmed SDK requirement remains consistently [catalystcentersdk >= 3.1.6.0.2] across all the modules.

Note: Provision Workflow Manager still uses python >= 3.9.
Addressing it in PR: #29

References:
https://pypi.org/project/catalystcentersdk/3.1.6.0.2/

Testing Done:

• [] Manual testing
• [] Unit tests
• [] Integration tests

Test cases covered: [Mention test case IDs or brief points]

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• All the sanity checks have been completed and the sanity test cases have been executed

Ansible Best Practices

• Tasks are idempotent (can be run multiple times without changing state)
• Variables and secrets are handled securely (e.g., using ansible-vault or environment variables)
• Playbooks are modular and reusable
• Handlers are used for actions that need to run on change

Documentation

• All options and parameters are documented clearly.
• Examples are provided and tested.
• Notes and limitations are clearly stated.

Screenshots (if applicable)

Notes to Reviewers